Skip to content

feat: update to solid-js@2.0.0-beta.15#565

Closed
atk wants to merge 2 commits into
solidjs:nextfrom
atk:next
Closed

feat: update to solid-js@2.0.0-beta.15#565
atk wants to merge 2 commits into
solidjs:nextfrom
atk:next

Conversation

@atk

@atk atk commented Jun 24, 2026

Copy link
Copy Markdown

No description provided.

@changeset-bot

changeset-bot Bot commented Jun 24, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: e537eaf

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@solidjs/router Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Comment thread .changeset/chilly-bottles-change.md Outdated
@atk atk changed the title feat: update to solid-js@2.0.0-beta.14 feat: update to solid-js@2.0.0-beta.15 Jul 7, 2026
ryansolid added a commit that referenced this pull request Jul 15, 2026
The beta migration itself landed separately (beta.18); this picks up the
vite-plugin-solid update (to current next.10) and the unused Params/
SetParams imports cleanup in utils.ts from that PR.

Co-authored-by: Cursor <cursoragent@cursor.com>
@ryansolid

Copy link
Copy Markdown
Member

Thanks @atk — this ended up superseded by the beta.18 update that just landed on next (bc38fb2), which covers the same migration surface (JSX types from @solidjs/web, jsxImportSource, the anchor attribute augmentation, structural RouterIntegration.signal, the delegateEvents signature change) plus the beta.16–18 changes like the owned-scope action guard. We also picked up your vite-plugin-solid bump and the unused-import cleanup from this branch (e31bb16). Appreciate you doing the groundwork here — closing in favor of the beta.18 update.

@ryansolid ryansolid closed this Jul 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants